Range header parsing

The main goals of this parser is:

• Follow specification RFC-2616
• Behave as expected MDN
• Accuracy - parses headers strictly
• Security - Never panics, ensured by fuzzing
• Stability
• No dependecies

Secondary goals are:

• Speed
• Information on why the header was rejected (feature 'with_error_cause')

The parser is strict. Any range where all parts are not syntactically correct and makes sense in the context of the underlying resource will be rejected.